Customizing Transaction Models and Mechanisms in a Programmable Environment Supporting Reliable Workflow Automation

A Transaction Specification and Management Environment (TSME) is a programmable system that supports: (i) implementation-independent specification of application-specific extended transaction models (ETMs), and (ii) configuration of transaction management mechanisms (TMMs) to enforce specified ETMs. The TSME can ensure correctness and reliability while allowing the functionality required by workflows and other advanced applications that require access to multiple heterogeneous, autonomous, and/or distributed (HAD) systems. To support ETM specification, the TSME provides a transaction specification language that describes dependencies between transactions. Unlike other transaction specification languages, TSME’s dependency descriptors use a common set of primitives, and are enforceable, i.e., can be evaluated at any time during transaction execution to determine whether operations issued violate ETM specifications. To determine whether an ETM can be enforced in a specific HAD system environment, the TSME supports specification of the transactional capabilities of HAD systems, and comparison of these with ETM specifications to determine mismatches. To enforce ETMs that are more restrictive than those supported by the union of the transactional capabilities of HAD systems, the TSME provides a collection of transactional services. These services are programmable and configurable, i.e., they accept instructions that change their behavior as required by an ETM, and can be combined in specific ways to create a run-time TMM capable of enforcing the ETM. We discuss the TSME in the context of a Distributed Object Management System. We give ETM specification examples and describe corresponding TMM configurations for a telecommunications application.